SD - Surya - Laxman - 2016-03-17 - 25812 - Spec - Default TAB as item category (Jeff by 2016-04-30) #OrderEntry
SPECIFICATIONS
25812-Spec-Default TAB as item category
Purpose
Default TAB as item category
Admin Info
Purpose
|
Default TAB as item category
|
Requested By
|
Jeff/ Jingsha
|
Spec Created By
|
Surya Basa/ Laxman
|
Spec Created Date
|
03/28/2016
|
Spec QA by
|
Surya Basa
|
Objects
|
|
Document Status
|
WIP
|
Estimates
Sl.No
|
Activity
|
Estimation in Hours
|
1
|
Research
|
|
2
|
Documentation
|
|
3
|
Development/ Config
|
|
4
|
Unit test in DEV
|
|
5
|
Unit test in QUA
|
|
6
|
Other activity
|
|
|
TOTAL
|
|
References
Prior Tickets
[Provide links of prior associated Spec / Break Fix BOSS document(s)]
Documents
[Attach any document(s) received for the requirement(s)]
Spec Changes
[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]
Sl.
|
Change Details
|
Requested By
|
Requested On
|
Notes if any
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Functional Requirement
Purpose/WHY:
[Explain the purpose of the project and the reason why this requirement has come]
To minimize the frequent change of Item category (TAS/TAB) in the sales order decided to specify the item category in the material master itself as BANS instead of BANC.
In Scope:
[List the
activities to be included in scope]
Out of Scope:
[Out of scope activities]
Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
To minimize the frequent change of Item category (TAS/TAB) in the sales order decided to specify the item category in the material master itself as BANS instead of BANC. To know the impact of this change New Era advised to run few test scenarios. Scenarios are given below.
[List test scenarios/cases to be executed here]
For New Materials
01
|
Standard order for a material with item category group BANS
|
02
|
Purchase-to-order for a material with item category group BANS
|
03
|
Dropship order for a material with item category group BANS
|
04
|
Quick Replenishment order for a material with item category group BANS
|
05
|
Contract for material with item category group BANS (plus call-off)
|
06
|
Credit Memo for material with item category group BANS
|
07
|
Return for material with item category group BANS
|
08
|
Debit Memo for material with item category group BANS
|
For Existing Materials.
01
|
Standard order for a material with item category group BANC. Update material to BANS. Update order from TAB to TAS.
|
02
|
Purchase-to-order for a material with item category group BANC. Update material to BANS. Update order from TAB to TAS.
|
03
|
Dropship order for a material with item category group BANC. Update material to BANS. Update order from TAB to TAS.
|
04
|
Quick Replenishment order for a material with item category group BANC. Update material to BANS. Update order from TAB to TAS.
|
05
|
Contract for material with item category group BANC (plus call-off). Update material to BANS. Update order from TAB to TAS.
|
06
|
Credit Memo for material with item category group BANC. Update material to BANS. Update order from TAB to TAS.
|
07
|
Return for material with item category group BANC. Update material to BANS. Update order from TAB to TAS.
|
08
|
Debit Memo for material with item category group BANC. Update material to BANS. Update order from TAB to TAS.
|
Later on decide that scenario 05 (contract creation with BANC) is not required.
Solution Details
[Provide complete technical details for configuration or programming here]
As advised ran the above said scenarios and forwarded for review. Please find below enclosed spread sheet. From the scenarios understand if the item category is changed from BANC to BANS no issues in the sales process.
ReCAP 25812 - Scenarios (2).xlsx
Issues
[List Issues / Bugs identified in configuration or development]